FIX OIDC token selection for sourcing "member_of" or "roles" claim #99
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem: "member_of" and "roles" claims in id_token ignored
Since there should also be an access_token, when something other than keycloak is being used, this function results in the id_token being ignored, regardless of whether or not the access_token contains the needed claims or not.
Fix: Checking the content of the access_token
checking the content of the access_token like this resolves the problem
if it does not contain the claims, we default to the id_token